Methods, systems, and computer readable media for user activated policy enhancement

ABSTRACT

According to one aspect, the subject matter described herein includes a method for subscriber activated policy enhancement. The method may include receiving a policy enhancement code from a user device at a policy enhancement server (PES). The method may further include obtaining at least one policy enhancement corresponding to the policy enhancement code in response to receiving the policy enhancement code from the user device. The method may further include enhancing at least one policy aspect of a policy for the user device based on the policy enhancement.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.13/244,245, filed Sep. 23, 2011, which claims the benefit of U.S.Provisional Patent Application Ser. No. 61/390,160 filed Oct. 5, 2010;the disclosures of which are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

The subject matter described herein relates to enhancement of networkaccess and/or network resource allocation policies. More specifically,the subject matter relates to methods, systems, and computer readablemedia for user activated policy enhancement.

BACKGROUND

A policy entity, such as a policy and charging rules function (PCRF) orpolicy engine, is a policy decision point that may be centrally locatedin the network and may communicate with access edge devices (e.g.,policy enforcement points), applications, and operational supportsystems/business support systems (OSS/BSS) platforms to managesubscriber access to network resources. The PCRF may collect subscriberand application data, authorize the allocation of network resources, andinstruct the user plane network elements on how to proceed with theunderlying data traffic. In one aspect, the PCRF may be connected to atleast one application function (AF) which includes a network elementresiding on the control plane representing applications that requiredynamic policy and QoS control over user plane behavior. Dynamic policyand charging control (PCC) rules can be derived within the PCRF usinginformation supplied by the AF. A policy and charging enforcementfunction (PCEF) may be connected to the PCRF on the control plane andmay provision PCC rules from the PCRF for policy enforcement. The PCCrules may be utilized for implementing service data flow (SDF) gatingand QoS controls associated with users in the network.

Collectively, the PCRF and PCEF may push or pull PCC rules derived fromthe AF to access edge devices where charging, SDF gating and QoS can beprovided. Triggering events such as roaming, volume, or durationcontrols may also be pushed back towards the AF for allowing theapplication to dynamically react to changes at the service level.Conventional systems may utilize predefined or pre-loaded PCC rules orcontrols which can be activated, enhanced, modified, and/or deactivatedat any time by the network operator or service provider. ConventionalPCRF architectures are not necessarily optimized to support emergingrevenue models that incorporate establishment of marketing campaignsbetween network operators and business partners. Such campaigns mayfacilitate methods of user activated policy enhancement via variousforms of marketing collateral.

Accordingly, and in light of such difficulties, a need exists formethods, systems, and computer readable media for user activated policyenhancement.

SUMMARY

According to one aspect, the subject matter described herein includes amethod for user activated policy enhancement. The method may includereceiving a policy enhancement code from a user device at a policyenhancement server (PES). The method may further include obtaining atleast one policy enhancement corresponding to the policy enhancementcode. The method may further include enhancing at least one policyaspect of a policy for the user device based on the policy enhancement.

A system for user activated policy enhancement is also disclosed. Thesystem may enable a user to activate a temporary change in a networkand/or a network resource allocation policy. In one embodiment thesystem may include a policy enhancement server (PES) and a policycontrol function. The PES may include a communications interface forreceiving a policy enhancement code from a user device. The PES mayfurther include a policy enhancement module for determining, using thepolicy enhancement code, a policy enhancement for the user. The policycontrol function may enhance at least one aspect of a policy for theuser device based on the policy enhancement.

The subject matter described herein for user activated policyenhancement may be implemented using a non-transitory computer readablemedium to having stored thereon executable instructions that whenexecuted by the processor of a computer control the processor to performsteps. Exemplary non-transitory computer readable media suitable forimplementing the subject matter described herein may include chip memorydevices and/or disk memory devices accessible by a processor,programmable logic devices, and application specific integratedcircuits.

As used herein, the term “node” refers to a physical computing platformincluding one or more processors and memory.

As used herein, the terms “function” or “module” refer to software incombination with hardware and/or firmware for implementing featuresdescribed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter described herein will now be explained with referenceto the accompanying drawings of which:

FIG. 1 is a network diagram showing an exemplary network for useractivated policy enhancement according to an embodiment of the subjectmatter described herein;

FIG. 2 is a message flow diagram illustrating user activated policyenhancement according to an embodiment of the subject matter describedherein;

FIG. 3 is a message flow diagram illustrating user activated policyenhancement according to another embodiment of the subject matterdescribed herein;

FIG. 4 is a block diagram illustrating an exemplary node for useractivated policy enhancement according to an embodiment of the subjectmatter described herein; and

FIG. 5 is flow chart illustrating exemplary steps for user activatedpolicy enhancement according to an embodiment of the subject matterdescribed herein.

DETAILED DESCRIPTION

The subject matter described herein includes methods, systems, andcomputer readable media for user activated policy enhancement. Asmentioned above, a policy entity or policy control function, such as apolicy and charging rules function (PCRF) may be connected to at leastone application function (AF) via a signaling interface, such as aDiameter-based Rx interface. The AF may include a network elementresiding on the service plane representing applications that requiredynamic policy and quality of service (QoS) control over transport planebehavior. Dynamic policy and charging control (PCC) rules can be derivedwithin the PCRF using information supplied, at least in part, by the AF.Advantageously, the present subject matter described herein providesnovel systems and methods for enabling user activated policy enhancementin a communications network, such as a Long Term Evolution (LTE)-basednetwork, Evolved Packet Core (EPS)-based network, or General PacketRadio Service (GPRS)-based network. For example, in one embodiment auser may activate new and/or enhanced policy rules for a predeterminedduration (e.g., the new and/or enhanced rules may be activated for 1hour). A user may activate or trigger new and/or enhanced rules to bederived using a policy enhancement code which can be communicated to apolicy enhancement server (PES). In one embodiment the PES includes anAF that communicates session information to PCRF via the Rx interface.The PES can communicate information for generation of new, modifiedand/or enhanced policy rules or policy elements, for example, PCC rulesto be supplied to the user's service at the policy and chargingenforcement function (PCEF). In an alternate embodiment, the PES may bea component of and/or be co-located with the PCRF.

By applying the subject matter described herein, network operators andtheir business partners may enter into marketing campaigns where, forexample, “coded” cards (e.g., with a bar code, near field communications(NFC) tag(s), radio frequency (RF) tag(s), Quick Response (QR) codes,etc.) or other marketing collateral may be distributed to subscribers orpotential subscribers and may include a “policy enhancement” code. Thepolicy enhancement code may allow a user to temporarily enhance networkaccess and/or network allocation policies in order to experience theenhancements before deciding whether or not to upgrade their serviceplan and/or purchase the marketed service (e.g., purchasing an upgradeto a new service plan). For example, a subscriber may use a smart phoneadapted to capture, detect, scan, read or otherwise acquire the policyenhancement code (e.g., a bar code value, a QR code, NFC/RFID tag code,a bar code image, or an alphabetic or numeric code read by the user andentered into the phone via a keypad) featured on the marketingcollateral. The policy enhancement code may be communicated to the PESand associated with new and/or enhanced policy elements or rules to beapplied to the subscriber's service at the PCEF. Such enhanced servicesmay include, for example, enhancements to max download bit rate,guaranteed download bit rate, download/upload quotas, allowed servicedata flow, and/or other network access or network resource allocationpolicies which can temporarily be made available to the subscriber. Incontrast to conventional architectures where policy elements or rulesmay only be activated or enhanced by network operators and/or serviceproviders, the subject matter described herein can allow the subscriberto quickly and easily enhance their existing network access and/orresource allocation policies via communication of the policy enhancementcode from marketing collateral to the PES.

Reference will now be made in detail to exemplary embodiments of thesubject matter described herein, examples of which are illustrated inthe accompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.

FIG. 1 is a network diagram showing an exemplary network for useractivated policy enhancement according to an embodiment of the subjectmatter described herein. FIG. 1 illustrates an exemplary communicationsnetwork 100 according to an embodiment of the subject matter describedherein. Referring to FIG. 1, network 100 may include user equipment (UE)102, an access node (AN) 104 (e.g., a base transceiver station (BTS) orevolved node b), a core network 106, and the Internet 108.

UE 102 represents a device, such as a mobile handset, for communicatingwith one or more portions of network 100. For example, UE 102 mayinclude a computer, a pager, a smartphone, a phone, a wireless modem, acomputing platform, a mobile handset, other subscriber devices and/orcombinations thereof. In one embodiment, UE 102 may be adapted todetect, capture, scan, read and/or otherwise acquire an opticallyscan-able code, such as a quick response (QR) or bar code. The actualbar code value (e.g., ‘123456’) may be obtained via a bar code readerdisposed on UE 102 or an image of the bar code may be acquired (e.g.,via a camera disposed on UE 102). The policy code may be obtained usingbar code image analysis as known in the art. Alternatively, the policyenhancement code may be entered by the user via the keypad of UE 102. UE102 may also include an NFC enabled device adapted to detect, capture,scan, and/or read NFC tags including, for example, RF identification(RFID) tags using an RFID reader integrated within the smart-phone ordevice. In further aspects, UE 102 may include a Bluetooth enableddevice capable of exchanging information over short distances using, forexample, short wavelength radio transmissions in the ISM band from2400-2480 MHz from fixed and/or mobile devices.

UE 102 may communicate with access node 104. Access node 104 may belocated within an access network (not shown). An access network mayinclude nodes, functions, devices, and/or components for providing a UE102 access to services, functions, or devices in one or more networks(e.g., core network 106). For example, an access network may include aradio access network (RAN) or other access network, such as a GlobalSystem for Mobile Communications (GSM) RAN (GRAN), a GSM enhanced datarates for GSM evolution (EDGE) RAN (GERAN), a general packet radioservice (GPRS) access network, a universal mobile telecommunicationssystem (UMTS) RAN (UTRAN), an evolved UTRAN (eUTRAN), an Internetprotocol (IP) connectivity access network (IP CAN), a code divisionmultiple access (CDMA) network, an Evolution-Data Optimized (EV-DO), awideband CDMA (WCDMA) network, a High Speed Packet Access (HSPA)network, or an evolved HSPA (eHSPA+) network.

Access node 104 may perform radio access functions for connecting UE 102with various communications networks and/or nodes. Access node 104 maycommunicate with core network 106 using gateway functionality. Forexample, access node 104 or other node (e.g., a gateway) may communicatemessages (e.g., authentication or mobility related messages) to one ormore nodes within the core network 106.

Core network 106 may include a network for providing services to UE 102.For example, core network 106 may perform network aggregation, charging,and authentication functions for UE 102. One or more PCC rules may beimplemented across core network 106 to facilitate network access and/ornetwork resource allocation policies including, for example, enablingthe detection of a service data flow (SDF) and providing parameters forpolicy and/or charging control. In one embodiment, core network 106 maybe at least one of a 3G network, a 3G+ network, a GSM network, a 4Gnetwork, an LTE network, an evolved packet core (EPC) network, a 3rdGeneration Partnership Project (3GPP) network, a GPRS core network, IMS,or other network.

Core network 106 may also include a PCEF 110 and a PCRF 112 whichcommunicate with each other to implement bandwidth, QoS, and chargingpolicies. Where core network 106 includes an IMS network, the policycontrol function, such as PCRF 112, may include a resource admissioncontrol subsystem (RACS). Core network 106 may also include other nodes,such as one or more AFs 114, a subscriber profile repository (SPR) 116,a Diameter relay agent and/or a Diameter signaling router (DRA/DSR), amobility management entity (MME), a home subscriber server (HSS), anauthentication, authorization, and accounting (AAA) server, and a BearerBinding and Event Reporting Function (BBERF).

In one embodiment, PCEF 110 may include any suitable entity forenforcing policies (e.g., via one or more policy rules or policyelements such as PCC rules). For example, PCEF 110 may includefunctionality located at a gateway (e.g., a packet data network (PDN)gateway) or other node for communicating between networks, e.g.,Internet 108 or private networks (not shown). In one embodiment, PCEF110 manages and enforces PCC rules provisioned from PCRF 112. Forexample, PCC rules may be provided to each service data flow (SDF)and/or UE 102 attempting to use or access PCEF 110 and may includeinformation for handling various traffic and situations. Exemplary PCEFnodes may include, but are not limited to, a Gateway GPRS Support Node(GGSN), a PDN gateway, a Deep Packet Inspection (DPI) node, and aTraffic Detection Function (TDF).

In one embodiment, PCC rules can be based on packet information suchthat a particular type of service or flow is policed differently fromother flows. For example, PCEF 110 may include a deep packet inspection(DPI) function for determining related packets (e.g., SDFs). A SDF maybe identified based on one or more common characteristics, including butnot limited to a common IP five-tuple. In one instance, PCC rules caninclude filters used for charging or policing SDFs. That is, PCC rulescan include definitions for charging a subscriber based on variouscharacteristics of usage (e.g., data size, data type, or individualmedia streams within a session). In this example, PCEF 110 may controlaccess to external networks and charge for such access based on rulesreceived from PCRF 112. PCRF 112 may derive policy elements or rules,for example, PCC rules using information provided by the one or more AFs114 and/or SPRs 116. In one embodiment, an AF 114 can include a node forallowing user activated policy enhancement, such as a policy enhancementserver (PES) 200. For example, PES 200 may include an AF or beintegrated with and/or co-located with AF 114 (FIG. 2). Alternatively,PES 200 may be a distinct node that is separate from AF 114 such asillustrated in FIG. 1. In further embodiments, PES 200 may be integratedwith and/or co-located with PCRF 112 (FIG. 4). Typically, PCRF 112accesses and implements predefined service policies provided by anetwork operator, subscriber information, and network-relatedinformation in determining policy decisions. Notably, the systems andmethods described herein allow individual subscribers or users toactivate one or more temporary changes or enhancements to their policiesvia policy enhancement information communicated to an AF which mayinclude PES 200, to PCRF 112 which may include PES 200 and/or to aseparate and distinct PES 200.

PCC rules may be communicated to PCEF 110 in various ways. For example,where PCEF 110 is located in or associated with the packet gateway, PCRF112 may push rules to PCEF 110 in the packet gateway (P-GW).Alternatively, rules may be pushed from PCRF 112 to PCEF 110 uponrequest from the PCEF 110. In further embodiments, a Gx interface usingDiameter protocol may be used to provision SDF based charging rules fromPCRF 112 to PCEF 110. PCEF 110 may then enforce the policy rulesreceived from PCRF 112 (e.g., by setting up and modifying bearers formapping IP service flows, by providing admission control, and byenforcing QoS limits).

Still referring to FIG. 1, in some embodiments, PCEF 110 may include orbe integrated with a gateway GPRS support node (GGSN) for communicatingbetween a GPRS network and external networks, e.g., Internet 108 orprivate networks (not shown). For example, in an embodiment where corenetwork 106 includes a GPRS core network, PCEF 110 may include a GGSN.PCEF 110 may communicate with serving GPRS support node (SGSN) or othergateway for providing services to UE 102. For example, PCEF 110 mayrequest and receive PCC rules from PCRF 112. Using the PCC rules, PCEF110 may control access to external networks and charge for such accessbased on the PCC rules. For example, for an SDF (e.g., one or morerelated packets) that is under policy control, PCEF 110 may allowpackets associated with the SDF to pass through the node if thecorresponding gate is open (e.g., as determined by one or more relevantPCC rules). For an SDF that is under charging control, PCEF 110 mayallow packets associated with the SDF to pass through the node if thereis a corresponding active PCC rule and, for online charging, the onlinecharging service (OCS) has authorized the applicable credit with thatcharging key. PCEF 110 may let packets associated with an SDF passthrough the gateway during the course of the credit re-authorizationprocedure. If requested by PCRF 112, PCEF 110 may report to PCRF 112when the status of the related SDF changes, which can be used to monitoran IP-CAN bearer path dedicated for AF signaling traffic.

In one embodiment, PCEF 110 includes a BBERF, or functionality thereof.The BBERF may be any suitable entity for performing bearer bindingand/or event reporting. In one embodiment, the BBERF may control userplane traffic. For example, the BBERF may ensure that an SDF is carriedover a bearer path with an appropriate QoS and may perform resourcereservation. The BBERF may also provide event reporting to one or morenodes in network 100. For example, the BBERF may inform PCRF 112 ofvarious network or bearer-related events, e.g., based upon eventtriggers installed or requested by PCRF 112. PCRF 112 and BBERF maycommunicate via a Gxx interface.

PCRF 112 may include any suitable policy entity or policy controlfunction for deriving, generating, obtaining, creating, selecting, orotherwise determining policies (e.g., one or more PCC rules). Forexample, PCRF 112 may include a stand-alone node, e.g., a policy serveror a multimedia policy engine (MPE), or may be co-located or integratedwith one or more nodes in network 100, e.g., a DRA/DSR. PCRF 112 mayinform PCEF 110, through the use of PCC rules, on the treatment of eachSDF that is under PCC control, in accordance with policy decisions. Inperforming policy decisions, PCRF 112 may communicate with one or morenodes in network 100 for gathering subscription related information. Forexample, PCRF 112 may communicate with AF 114 and/or PES 200 via an Rxinterface to retrieve policy and charging information. Alternatively,PCRF 112 may communicate with SPR 116 via an Sp interface to retrievepolicy and charging information. In another example, PCRF 112 maycommunicate with a network management system (NMS), e.g., via a simplenetwork management protocol (SNMP) interface. In this example, PCRF 112may poll or otherwise query the NMS or a related database to receiveinformation, e.g., regarding the state of one or more devices in anaccess network, core network, or other network.

Still referring to FIG. 1, PCC rules or other policy decisions generatedat PCRF 112 may be based on one or more of the following: informationobtained from one or more AFs 114 and/or PES 200 via an Rx interface(e.g., session, media, and subscriber related information), informationobtained from PCEF 110 (e.g., IP-CAN bearer attributes, request type,device information, and subscriber related information), informationobtained from SPR 116 (e.g., subscriber and service related data),pre-configured information, and/or combinations thereof. As mentionedabove, AF 114 includes a network element offering applications thatrequire dynamic policy and/or charging control over the IP-CAN userplane behavior. In one embodiment AF 114 may include PES 200 and may beconfigured to implement user activated policy enhancement upon receiptof a policy enhancement code as described further below. In furtherembodiments, PES 200 may be a distinct node that is separate from AF 114which can be configured to implement user activated policy enhancementupon receipt of a policy enhancement code as described further below. Inone embodiment, AF 114 may include a proxy-call session control function(P-CSCF) of an IMS network.

In one embodiment, an Rx interface is used to exchange dynamicapplication level session information between AF 114 and PCRF 112 and/orbetween PES 200 and PCRF 112, as well as IP-CAN specific information andnotifications about IP-CAN bearer level events. Session information fromAF 114 and/or PES 200 may include part of the input used by PCRF 112 togenerate dynamic PCC decisions and derive QoS for the applicationsession. In one embodiment, session information includes informationabout the AF session (e.g. including but not limited to applicationidentifier, type of media, bandwidth, IP address and port number). Toinitiate an initial AF or PES session, which may require one or more PCCrules, AF 114 or PES 200 may open an Rx Diameter session with PCRF 112for the AF or PES session using an Rx specific Auth-Application Request(AAR) command. AF 114 or PES 200 may provide UE identifying informationsuch as, an International Mobile Station Identifier (IMSI), an IMSpublic or private identity, a Mobile Subscriber ISDN (MSISDN)identifier, or the IP address of the UE (e.g., UE 102) and correspondingsession information using one or more attribute value pairs (AVPs). AF114 or PES 200 may indicate to PCRF 114 whether the media IP flow(s)should be enabled or disabled using a flow-status AVP. AF 114 or PES 200may provide session information to PCRF 112 that has been fullynegotiated (e.g. based on a session description protocol (SDP) answer tothe AAR) or not fully negotiated (e.g., based on an SDP offer to theAAR). In the fully negotiated case, PCRF 112 may authorize the sessionand provision corresponding PCC and QoS rules to PCEF 110. In the notfully negotiated case and upon receipt of such preliminary sessioninformation, PCRF 112 may perform an early authorization check of thesession information and may authorize PCC and/or QoS rule requestsreceived from PCEF 110.

AF 114 or PES 200 may modify the session information at any time (e.g.due to an AF session modification or internal AF trigger controls) bysending an AAR command to PCRF 112 containingmedia-component-description AVP(s) with updated session information. IfAF 114 or PES 200 provides service information that has been fullynegotiated, PCRF 112 may authorize the session and provisioncorresponding PCC and/or QoS rules to PCEF 110. In one embodiment, PCRF112 may process the session information received from AF 114 or PES 200according to operator policy and may decide whether the request will beaccepted or not. If the modified and/or updated session information isnot acceptable (e.g. subscribed guaranteed bandwidth for a particularuser is exceeded), PCRF 112 may indicate in the AA-Answer the cause forthe rejection. The PCRF may additionally provide the acceptablebandwidth within the Acceptable-Service-Info AVP.

Depending on the application, AF 114 or PES 200 may instruct PCRF 112when the IP flow(s) are to be enabled or disabled to pass through theIP-CAN. AF 114 or PES 200 may do this by sending an AAR messagecontaining the flow status information (i.e., in a Flow-Status AVP) forthe flows to be enabled or disabled. In response to this action, PCRF112 may determine and set an appropriate gate status for thecorresponding active PCC rule(s). When an AF or PES 200 session isterminated, if AF 114 or PES 200 had received a successful AA-Answer tothe initial AAR, AF 114 or PES 200 may send aSession-Termination-Request command to PCRF 112. Otherwise, AF 114 orPES 200 may wait for the initial AA-Answer to be received prior tosending the Session-Termination-Request command to PCRF 112. During thesession, AF 114 or PES 200 may request PCRF 112 to report on thesignaling path status for the AF session. The AF shall cancel therequest when AF 114 ceases handling UE 102′.

As noted earlier, PES 200 may include an AF 114 and/or be integratedwith and/or co-located at AF 114 (e.g., see FIG. 2). In otherembodiments, PES 200 may include a node that is separate and distinctfrom AF 114 and/or PCRF 112 as illustrated in FIG. 1. In furtherembodiments, PES 200 may be integrated with and/or co-located at PCRF112 (e.g., see FIG. 4). Referring to FIG. 1, network 100 may include PES200 for providing user activated policy enhancement. PES 200 may receivea policy enhancement code communicated from a user device, for example,UE 102. The policy enhancement code may be acquired by UE 102 usingpreviously described methods (e.g., optically scanning a bar code,manual entry of a code upon a keypad of UE 102, NFC scan, Bluetoothbeacon scan, etc.) and may be communicated to PES 200 using, forexample, an SMS message, a MMS message, an IM, an email message, an XMLmessage, a simple object access protocol (SOAP) message, a Diameterprotocol message, a SIP message, etc. Upon receipt of the policyenhancement code information, PES 200 may obtain at least one policyenhancement and/or enhanced policy aspect for the user devicecorresponding to the policy enhancement code. Such policy enhancementand/or enhanced policy aspect may include, without limitation,enhancement to one or more aspects of a user's network services such asmaximum guaranteed download bit rate, maximum download bit rate,permitted service flow, permitted QoS class, permitted APN, permitteddestination IP address or port, and/or upload/download quota. The policyenhancement may be communicated to PCRF 112 from PES 200 via an Rxinterface in a policy enhancement update request and/or notificationmessage. The policy update notification message may include a subscriberID associated with a user of UE 102 and the specific policy enhancementassociated with the policy enhancement code value. Upon receipt of therequest or notification message, PCRF 112 may generate at least one newor updated PCC rule associated with the policy enhancement code, andcommunicate the new or updated PCC rule to PCEF 110.

As described earlier, PCC rules may be based upon and/or includeinformation for managing user plane traffic (e.g., data packets). Forexample, a PCC rule may include one or more of a (1) rule name, (2)service identifier, (3) SDF filter(s), (4) precedence information, (5)gate status, (6) QoS parameters, (7) charging key (i.e., rating group),(8) other charging parameters, and/or (9) monitoring key. Suchinformation may be enhanced, modified, and/or re-generated upon captureand association of a policy enhancement code to PES 200, for example, byscanning a bar code, reading a NFC or RFID tag, typing a code into akeypad of UE 102 or via Bluetooth signaling.

The rule name or PCC rule identifier may be used to reference a PCC rulein the communication between PCEF 110 and PCRF 112 and may be unique foreach PCC rule used during an internet protocol connectivity accessnetwork (IP-CAN) session. The service identifier may be used to identifythe service or the service component to which the SDF relates. The SDFfilter(s) may be used to select the traffic for which the rule applies.For example, an SDF filter make take the form of an IP five-tuplespecifying: (1) source IP address(es), (2) destination IP address(es),(3) source port number(s), (4) destination port number(s), and (5)application protocol(s) (e.g., transmission control protocol (TCP), userdatagram protocol (UDP)). In this example, packets containinginformation matching the IP five-tuple may be considered part of the SDFfor which the corresponding PCC rule is to be applied. In anotherexample, an SDF filter may be based on fewer, different, and/oradditional criteria. For example, UE 102 or another node in network 100may assign an SDF identifier (e.g., a value) to packets in a customparameter field. In this example, an SDF filter in a PCC rule may usethis value for determining traffic to which the PCC rule applies.

Precedence information may define the order in which PCC rules areapplied (e.g., at PCEF 110) for a given SDF. For example, wheredifferent PCC rules are activated that have overlapping SDF filters,precedence information determines which rules are applicable and/or whenthe rule is to be applied. In some instances, when a dynamic PCC rule(e.g., based upon information supplied from AF 114 and/or PES 200) and apredefined PCC rule (e.g., based upon information supplied from SPR 116)are activated, precedence information may indicate that the dynamic PCCrule is take precedence, or vice versa. Gate status may indicate whetherthe SDF, as detected by the SDF filter(s), may pass (i.e., when gate isopen) or may be discarded (i.e., when gate is closed) in uplink and/orin downlink direction. QoS information includes the QoS class identifier(e.g., authorized QoS class for the SDF), the Allocation and RetentionPriority (ARP), and authorized bit rates for uplink and downlink.Charging parameters may define whether online and offline charginginterfaces are used, what is to be metered in offline charging, and onwhat level PCEF 110 shall report the usage related to the rule. Othercharging parameters may include AF record information for enablingcharging correlation between the application and bearer layer if AF 114has provided this information via the Rx interface. The monitoring keyfor a PCC rule may identify a monitoring control instance that may beused for usage monitoring control of the SDFs controlled by thepredefined PCC rule or dynamic PCC rule.

It will be appreciated that FIG. 1 is for illustrative purposes and thatvarious nodes, their locations, and/or their functions may be changed,altered, added, or removed. For example, some nodes and/or functions maybe combined into a single entity, e.g., AF 114 and PCRF 112 may beincluded in an MPE. In a second example, a node and/or function may belocated at or implemented by two or more nodes.

FIG. 2 is block diagram illustrating an exemplary node or PES 200 forfacilitating user activated policy enhancement according to anembodiment of the subject matter described herein. In one embodiment,PES 200 includes an AF (e.g., previously described AF 114) for dynamicpolicy enhancement and may include a stand-alone node or may beintegrated with additional functionality or another node. For example,PES 200 may be integrated with, include, or be co-located at PCRF 112.In one embodiment, PES 200 provides dynamic information to PCRF 112 viaRx interface for generation of one or more PCC rules. Communication ofthe information to PCRF 112 can be activated or triggered when a userprovides a policy enhancement code to PES 200 via UE 102 (e.g., UE 102may communicate the code to PES 200 via a short message service (SMS)message, a multimedia message service (MMS) message, an instant message(IM), an email message, an XML message, a simple object access protocol,a Diameter protocol message, a session initiation protocol (SIP)message, or other suitable message protocol/format).

Referring to FIG. 2, PES 200 may receive a policy enhancement code froma communications device (e.g., UE 102) at block 202 via a firstcommunications interface 204 (e.g., via a Gx interface, Gxx interface,Sp interface, an extensible markup language (XML) interface, a sessioninitiation protocol (SIP) interface, a SOAP interface, or a hypertexttransfer protocol (HTTP) interface, Diameter, Radius, LDAP or others).The policy enhancement code may be acquired via UE 102, for example, byscanning a bar code to obtain a scanned value, using a camera to capturean image of a bar code, using an NFC/RFID reader to detect an NFC/RFIDtag code, or Bluetooth or other radio frequency (RF) or infrared (IR)signaling, or via manual input using the keypad of UE 102.

As noted earlier, the acquired policy enhancement code may becommunicated to PES 200 using one of a SMS message, a MMS message, anIM, an email message, an XML message, a simple object access protocol, aDiameter protocol message, and/or a SIP message. In one embodiment, UE102 includes a Bluetooth, RF, and/or IR receiver to receive or detect anRF/IR beacon signal which provides the policy enhancement code to beused for policy enhancement. Policy enhancement codes may be adapted totrigger a temporary enhancement to and/or change in network access,network resource allocation, and/or usage policies for the subscriber bysignaling UE 102. The acquired policy enhancement code may becommunicated to PES via first interface 204 and associated with enhancedsubscriber policy elements at PES 200. The enhanced policy elements orPCC rules and/or information about useful for PCC rule generation maythen be signaled to PCRF 112 and/or RAGS (i.e., in an IMS network) forenhancement of a subscriber's service across one or more networks. Inone embodiment, the policy enhancement code may enhance and/or changeone or more aspects of the subscribers control and charging policyincluding but not limited to the maximum guaranteed D download bit rate,maximum download bit rate, permitted service flow, permitted QoS class,permitted access point name (APN), permitted destination IP address orport, and/or upload/download quota.

In one embodiment, PES 200 may include a policy enhancement module 206in communication with a policy enhancement database 208. Upon receivingthe policy enhancement code, policy enhancement module 206 may query,using the acquired code, policy enhancement database 208 to determinepolicy enhancements or enhanced policy aspects provisioned from thecode. Policy enhancement database 208 may also log the date and timethat the user activated policy enhancement request was received. In oneembodiment, the policy enhancement code may include a numeric and/oralphanumeric value (e.g., ‘123456789’) which may be associated with oneor more policy enhancements to one or more of a user's policy aspects(e.g., enhanced maximum guaranteed download bit rate, maximum downloadbit rate, permitted service flow, permitted QoS class, permitted APN,permitted destination IP address/port, download quota) within policyenhancement database 208. In other aspects, policy enhancement code mayinclude an image of a bar code where PES 200 is adapted to process theimage so as to determine the associated policy enhancement code valueprior to association with policy elements via querying policyenhancement database 208.

Policy enhancement database 208 may be integrated or co-located with PES200 as illustrated, or it may be located at a node distinct from PES200. Policy enhancement database 208 may access policy information andstore log information based on the date and time of the user request forpolicy enhancement. Policy database 208 may be pre-configured (e.g., byoperator at an initial time) and/or may retrieve or learn associationsfrom another source (e.g., a master policy enhancement database). Anexample of exemplary policy information that may be stored in policyenhancement database 208 for querying, using a policy enhancement codeis shown below in Table 1 below. For example, in Table 1, associationsbetween the policy enhancement code value, subscriber identifiers (ID),and the guaranteed download bit rate aspect of a subscriber's controland charging policy are illustrated. Other associations may be made inthe same and/or a different policy enhancement database 208, forexample, associations between policy enhancement code value, subscriberID and one or more of maximum download bit rate, permitted service flow,permitted QoS class, permitted APN, permitted destination address/port,and download quota.

In Table 1, associations between policy enhancement code values (i.e.,scan code value), subscriber ID, the enhanced policy value (e.g.,guaranteed download bit rate), duration, and enhancement activation areillustrated. Table 1 includes six columns: ‘Scan code value’,‘Guaranteed Download Bit rate’, ‘Duration’, ‘Active’, ‘Subscriber ID’,and ‘Use Date/Time’. The first column includes the value of the policyenhancement code acquired using UE 102 and communicated to PES 200. Thevalue may scanned/captured/acquired via UE 102 (e.g., using a bar codereader/scanner, camera, NFC/RFID reader, Bluetooth or RF/IR signaling)and communicated to PES 200 via one of an SMS message, an MMS message,an instant message, an email message, an XML message, a simple objectaccess protocol, a Diameter protocol message, a SIP message, etc. In thealternative, the scan code value may be associated with a bar code imageprocessed at PES 200. PES 200 may associate the policy enhancement orscan code value with one or more specific policy enhancements (e.g.,increase in guaranteed download bit rate, maximum download bit rate,download quota etc.) via querying policy enhancement database 208. Thesecond column ‘Guaranteed Download Bit rate’ includes the specificpolicy enhancement aspect associated with the code. For example, thevalue ‘123456789’ is associated with a 25 percent (%) increase inguaranteed download bit rate. The subscriber's service will receive theenhanced download bit rate for one hour as indicated by the ‘Duration’column. The ‘Active’ column indicates whether or not the enhancement isactive, that is, whether a user has yet to activate the enhanced policyby acquiring the code. The ‘Subscriber ID’ column includes varioussubscriber identifiers for identifying a user associated with the policyinformation. For example, the scan code value ‘987654321’ has beenactivated by user ‘Sub 1’. The time and date of the user activation maybe logged in the ‘Use Date/Time’ column. For example, user ‘Sub 1’activated the policy enhancement on Oct. 1, 2011. A time element may beprovided as well.

TABLE 1 Table 1: Exemplary Policy Information That May Be Stored at orIn Policy Enhancement Database Guaranteed Scan code Download SubscriberUse value Bit rate Duration Active ID Date/Time 123456789 +25%  1 hourYes — — 987654321 +25% 30 min No Sub 1 Oct. 1, 2011

Policy enhancement module 206 may query policy enhancement database 208to determine one or more specific associated policy enhancements, whichmay then be communicated via Rx interface 210 to PCRF/RACs as indicatedby block 212. For the example above, the 25% increase in guaranteeddownload bit rate can be communicated to PCRF 112 over Rx interface 210via policy enhancement module 206. In response to being notified of therequested change and/or enhancement to one or more aspects of thesubscriber's control and charging policy (e.g., 25% increase inguaranteed download bit rate), PCRF 112 may generate one or moreassociated PCC rules and communicate rules to PCEF 110. PCEF will thenenforce the new PCC rules and charge accordingly. The enhancement willthen be enforced for the associated duration (e.g., 30 min).

FIGS. 3 and 4 are message flow diagrams illustrating user activatedpolicy enhancement according to embodiments of the subject matterdescribed herein. In a first embodiment as illustrated by FIG. 3, atstep 301 UE 102 requests and is granted connectivity to an IP PacketData Network (PDN). For example, an Access Point Name (APN) may identifythe PDN associated with PES/AF 200 that the user wishes to communicatewith. At step 302, a user of UE 102 identified by ‘Sub 1’ may acquire apolicy enhancement code. Again, the policy enhancement code may beavailable from promotional or marketing collateral and may allow a userto temporarily enhance aspects of their control and charging policy, forexample, guaranteed download bit rate, maximum download bit rate, QoS,permitted QoS class, etc. The policy enhancement code may be acquired byusing a camera associated with UE 102 to scan or capture a bar code tobe used for policy enhancement. UE 102 may also acquire a bar code usingan NFC/RFID reader to acquire tag information to be used for policyenhancement or Bluetooth or other RF/IR signaling.

At step 303, UE 102 initiates and communicates a policy enhancementrequest message to PES/AF 200. The policy enhancement request messagemay include the policy enhancement code value (e.g., ‘123456789’) andthe user subscriber ID (e.g., Sub 1). The policy enhancement code valueand user subscriber ID are associated with a new and/or enhanced aspectof the subscriber's control and charging policy (e.g., 25% increase inguaranteed download bit rate). PES/AF 200 initiates and communicates apolicy update notification message (e.g., an AAR command containingAVP(s)) to PCRF 112 at step 304. The policy update notification messagemay include the subscriber ID (e.g., Sub 1) and the specific policyenhancement associated with the policy enhancement code value. At step305, PCRF 112 may signal a re-Auth Request (RAR) message to PCEF 110with an updated charging rule for Sub 1. For example, PCRF 112 maygenerate a new PCC rule based upon information received in the updatenotification message received from PES/AF 200. At step 306, PCEF 110sends PCRF 112 a re-Auth Answer (RAA) message indicating receipt of thenew and/or updated PCC rule and PCRF 112 indicates or signals anacknowledgment (ACK) to PES/AF 200 at step 307. Accounting and billingrecords may then be generated according to the new or enhanced PCCrule(s) at step 308. The new or enhanced PCC rule(s) may be in effectfor the duration specified by policy enhancement database 208 at PES/AF200.

FIG. 4 illustrates a message flow diagram for a second embodiment ofuser activated policy enhancement. In this embodiment, PES 200,including policy enhancement database 208 may be integrated and/orco-located with PCRF 112. At step 401, UE 102 requests and is grantedconnectivity to an IP PDN for a given APN. At step 402, UE 102 acquiresa policy enhancement code as previously described. At step 403, UE 102initiates and communicates a policy enhancement request message to PCRF112. The policy enhancement request message may include the subscriberID (e.g., Sub 1) and the policy enhancement code value (e.g., ‘12345679’or an optical image to be associated with a value). The value isassociated with an updated charging rule for Sub 1 generated at PCRF112. PCRF 112 may communicate the updated charging rule for Sub 1 toPCEF 110 via an RAR message as indicated at step 404. PCEF 110 mayacknowledge the updated charging rule via the RAA message communicatedto PCRF 112 at step 405. At step 406, PCRF 112 may communicateaccounting and/or billing records per the updated or enhanced chargingand control rules.

FIG. 5 is a flow chart illustrating an exemplary process for useractivated policy enhancement according to an embodiment of the subjectmatter described herein. In some embodiments, the exemplary processdescribed herein, or portions thereof, may be performed by UE 102, PES200, and/or PCRF 112.

Referring to FIG. 5, in step 500, acquired policy enhancement code maybe received at a PES, such as PES 200. As described earlier, PES 200 mayinclude an AF (e.g., AF 114) or be integrated with and/or co-located atAF 114. In other embodiments, PES 200 may be integrated with and/orco-located at PCRF 112. In further embodiments, PES 200 may be a nodethat is separate and distinct from AF 114 and/or PCRF 112. The policyenhancement code may include a numeric or alphanumeric code valueacquired by a user device (e.g., UE 102) for example by scanning a barcode, reading an NFC or RFID tag, manually entering the code into akeypad of UE 102, or acquiring the code via Bluetooth signaling. A barcode image may also be acquired for which PES 200 may be adapted toassociate with a value. The policy enhancement code may be associatedwith one or more policy enhancements or enhanced subscriber policyelements that may be temporarily activated for a given duration. Forexample, the code may guarantee a max download bit rate for a givenduration, such as one hour.

In step 502, at least one policy enhancement (e.g., enhancements to oneor more of a maximum guaranteed download bit rate, a maximum downloadbit rate, a permitted service flow, a permitted QoS class, a permittedaccess point name (APN), a permitted destination IP address/port, and/ora download quota) may be obtained. The policy enhancement may correspondto the policy enhancement code. At PES 200, the code may be associatedwith new and/or enhanced policy information to be activated for aspecified duration for a specified user. For example, a policyenhancement module 206 within PES 200 may query policy enhancementdatabase 208 using the policy enhancement code to obtain policyenhancement(s) corresponding to the code. PES 200 may log use of thecode by the requesting user or subscriber.

In step 504, at least one aspect of a policy for the user device basedon the policy enhancement may be enhanced. For example, a PCC ruleassociated with the policy enhancement code may be generated ormodified. In one embodiment, PES 200 may contact PCRF 112 via Rxinterface 210 and communicate policy information indicating modifiedsession information and/or new policy rules for the subscriber. PCRF 112may use the obtained policy information, or a portion thereof, togenerate one or more associated PCC rules or policy decisions andcommunicate the PCC rules to PCEF 110 as indicated at step 506.

It will be understood that various details of the subject matterdescribed herein may be changed without departing from the scope of thesubject matter described herein. Furthermore, the foregoing descriptionis for the purpose of illustration only, and not for the purpose oflimitation, as the subject matter described herein is defined by theclaims as set forth hereinafter.

What is claimed is:
 1. A method for providing user activated policyenhancement, the method comprising: at a policy enhancement server(PES), receiving a policy enhancement code from a user device; inresponse to receiving the policy enhancement code from the user device,obtaining at least one policy enhancement corresponding to the policyenhancement code; and enhancing at least one policy aspect of a policyfor the user device based on the policy enhancement by generating atleast one policy and charging control (PCC) rule based on the policyenhancement and communicating the at least one PCC rule to a policy andcharging enforcement function (PCEF).
 2. The method of claim 1, whereingenerating the at least one PCC rule includes communicating the policyenhancement to a policy and charging rules function (PCRF) or a resourceadmission control subsystem (RACS).
 3. The method of claim 2, whereinthe PES is integrated or co-located with the PCRF or the RACS.
 4. Themethod of claim 1, wherein receiving the policy enhancement code fromthe user device comprises receiving the code from a camera associatedwith the user device to capture an optical scan code containing thepolicy enhancement code.
 5. The method of claim 1, wherein receiving thepolicy enhancement code from the user device comprises receiving thecode from a near-field communication (NFC) reader, a radio frequencyidentification (RFID) reader, or a bar code reader associated with amobile communication device to obtain the policy enhancement code vianear field, RF communications, or bar code image analysis.
 6. The methodof claim 1, wherein receiving the policy enhancement code from the userdevice includes using a Bluetooth or other radio frequency (RF) orinfrared receiver (IR) to detect an RF/IR beacon signal which providesthe policy enhancement code.
 7. The method of claim 1, wherein receivingthe policy enhancement code includes receiving at least one of a shortmessage service (SMS) message, a multimedia message service (MMS)message, an instant message (IM) message, an email message, an XMLmessage, a simple object access protocol, a Diameter protocol message,and a session initiation protocol (SIP) message that contains the policyenhancement code.
 8. A system for user enhancement of policy control,the system comprising: a policy enhancement server (PES) including: acommunications interface for receiving a policy enhancement code from auser device, wherein the user device is configured to detect, read, oracquire the policy enhancement code; and a policy enhancement module fordetermining, using the policy enhancement code, a policy enhancement forthe user; and a policy control function for enhancing at least oneaspect of a policy for the user device based on the policy enhancementby generating at least one policy and charging control (PCC) rule andcommunicating the at least one PCC rule to a policy and chargingenforcement function (PCEF).
 9. The system of claim 8, wherein thepolicy control function includes a policy and charging rules function(PCRF) or a resource admission control subsystem (RACS).
 10. The systemof claim 9, wherein the PES is integrated or co-located with the PCRF orthe RACS.
 11. The system of claim 8, wherein the PES is integrated orco-located with an application function (AF).
 12. The system of claim 8,wherein the user device is configured to detect, read, and/or acquirethe policy enhancement code.
 13. The system of claim 12, wherein theuser device comprises a camera associated with a mobile communicationdevice to capture an optical scan code to be used for policyenhancement.
 14. The system of claim 12, where the user device comprisesa near-field communication (NFC) reader, a radio frequencyidentification (RFID) reader, or a bar code reader associated with amobile communication device.
 15. The system of claim 12, wherein theuser device comprises a Bluetooth or other radio frequency (RF) orinfrared receiver (IR) to detect an RF/IR beacon signal which providesthe policy enhancement code.
 16. The system of claim 8, wherein the PESis configured to receive the policy enhancement code via at least one ofa short message service (SMS) message, a multimedia message service(MMS) message, an instant message (IM) message, an email message, an XMLmessage, a simple object access protocol, a Diameter protocol message,and a session initiation protocol (SIP) message from the user device.17. A non-transitory computer readable medium having stored thereoncomputer executable instructions that when executed by a processor of acomputer control the computer to perform steps comprising: at a policyenhancement server (PES), receiving a policy enhancement code from auser device; in response to receiving the policy enhancement code fromthe user device, obtaining at least one policy enhancement correspondingto the policy enhancement code; and enhancing at least one policy aspectof a policy for the user device based on the policy enhancement bygenerating at least one policy and charging control (PCC) rule based onthe policy enhancement and communicating the at least one PCC rule to apolicy and charging enforcement function (PCEF).